webextensions.api.userScripts - Missing execute method

[erosman]

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

execute method is already implemented by Chrome

• execute()
• Implement userScripts.execute

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

Method listed

Did you test this? If so, how?

n/a

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/userScripts

MDN metadata

MDN page report details

• Query: webextensions.api.userScripts
• Report started: 2025-05-29T16:52:23.849Z

[caugner]

We don't currently document Chrome-only WebExtensions APIs in BCD or on MDN.

/cc @rebloor

[caugner]

This feature is actually tracked for implementation in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1930776

So we can probably go ahead and add this data.

And while we're here, we could also add this Safari impl_url for webextensions.api.userScripts: https://bugs.webkit.org/show_bug.cgi?id=271472

[erosman]

We don't currently document Chrome-only WebExtensions APIs in BCD or on MDN.

MDN has become the primary reference site for JavaScript & browser API, and not only for Firefox.
There are many entries on MDN that are not supported by Firefox yet, and some that are not even planned.
IMHO, it is good to cover all related data.

Examples

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/notifications/NotificationOptions
https://developer.mozilla.org/en-US/docs/Web/API/Navigation/navigate
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import/with with {type: 'css'})

See also

#17635 (comment)

We don't track features that aren't implemented in any browser in BCD, so I'm going to close this issue.

mdn/content#29555 (comment)

Does it make sense to document this parameter already, even if Firefox doesn't support it yet?

As an example, please note notifications: Browser compatibility & notifications.TemplateType which include many items that Firefox does not support and has no plans to support.